• I'm the package's author and/or maintainer.
• I have read the docs.
• I have tagged a release with a semver version number.
• My package repo has a description and a README describing what it's for and how to use it.
• My package doesn't add context menu entries. *
• My package doesn't add key bindings. **
• Any commands are available via the command palette.
• Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
• If my package is a syntax it doesn't also add a color scheme. ***
• I use .gitattributes to exclude files from the package: images, test files, sublime-project/workspace.

My package adds syntax highlighting for Interactive Shader Format (ISF) files. ISF is a GLSL-based format for describing GPU shaders, widely used in VJ tools, creative-coding environments, and video-effects hosts such as VDMX, ISF editors on the web, and similar applications. Fragment shaders are typically saved as .fs, vertex shaders as .vs, and combined documents as .isf; all three extensions are registered.

The package is a pure syntax contribution — no commands, menus, key bindings, color schemes, or settings UI. It extends standard GLSL highlighting with ISF-specific awareness: the JSON metadata block in the leading /* { ... } */ header, ISF uniforms (PASSINDEX, RENDERSIZE, isf_FragNormCoord, TIME, TIMEDELTA, DATE, FRAMEINDEX), ISF image-sampling macros (IMG_PIXEL, IMG_NORM_PIXEL, IMG_SIZE, IMG_THIS_PIXEL, IMG_THIS_NORM_PIXEL, isf_vertShaderInit), and ISF input types (event, bool, long, float, point2D, color, image, audio, audioFFT).

It is forked from euler0/sublime-glsl, which provides only plain GLSL highlighting and has no ISF awareness. There are no packages like it in Package Control.